User presence aggregation at a server

ABSTRACT

A presence aggregation system provides a presence aggregation server that allows for the publication of presence state of a publisher from the publisher&#39;s multiple endpoints. A presence state includes an availability value and an activity. An activity may include an activity token and/or a custom string. When any one of the publisher&#39;s endpoints makes a presence state publication on the presence aggregation server, the presence aggregation server generates an aggregated state of the publisher (i.e., the availability of the publisher aggregated across all of the publisher&#39;s endpoints) and publishes the generated aggregated state to each of the publisher&#39;s endpoints. The presence aggregation server may also provide the publisher&#39;s aggregated state to the subscribers of the publisher&#39;s aggregated state information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patentapplication Ser. No. 14/967,105, filed on Dec. 11, 2015, and entitled“USER PRESENCE AGGREGATION AT A SERVER,” which is a continuationapplication of U.S. patent application Ser. No. 11/419,947, filed on May23, 2006, issued as U.S. Pat. No. 9,241,038, and entitled “USER PRESENCEAGGREGATION AT A SERVER,” both of which are incorporated herein in theirentirety by reference.

This application is related to U.S. patent application Ser. No.11/392,472, entitled “Aggregating User Presence Across MultipleEndpoints,” which was filed on Mar. 28, 2006, issued as U.S. Pat. No.7,945,612, and U.S. patent application Ser. No. 11/392,991, entitled“User Interface For User Presence Aggregated Across Multiple Endpoints,”which was filed on Mar. 28, 2006, the disclosures of which areincorporated by reference herein in their entireties.

BACKGROUND

Users of computing devices (e.g., laptops, cellular phones, and personaldigital assistants) often need to communicate in real time. A commonform of real-time communications is provided by instant messagingservices. An instant messaging service allows participants at endpointsto send messages and have them received within a second or two by theother participants in a conversation. The receiving participants canthen send responsive messages to the other participants in a similarmanner. To be effective, a real-time conversation relies on theparticipants' becoming aware of, reviewing, and responding to receivedmessages very quickly. This quick response is in contrast toconventional electronic mail systems in which the recipients ofelectronic mail messages respond to messages at their convenience.

When an initiating participant wants to start a real-time conversation,that participant needs to know whether the intended participants areavailable to respond in real time to a message. If not, thencommunications via conventional electronic mail, voice mail, or someother mechanism may be more appropriate. For example, if the computersof the intended participants are currently powered off, then a real-timeconversation may not be possible. Moreover, if their computers arecurrently powered on, but the intended participants are away from theircomputers, a real-time conversation is also not possible. The initiatingparticipant would like to know the availability of the intendedparticipants so that an appropriate decision on the form ofcommunication can be made.

Presence services provide this availability information. Theavailability status of an entity such as a computer system or a userassociated with that computer system is referred to as “presenceinformation.” Presence information identifies the current “presencestate” of the user. Users make their presence information available to apresence service so that other users can decide how best to communicatewith them. For example, the presence information may indicate whether auser is logged on (“online”) with an instant messaging server or islogged off (“offline”). Presence information may also provide moredetailed information about the availability of the user. For example,even though a user is online, that user may be away from their computerin a meeting. In such a case, the presence state may indicate “online”and “in a meeting.”

In an instant messaging context, a publishing user (“publisher”) mayprovide their presence information to a presence server that thenprovides the presence information to subscribing users (“subscribers”).Thus, a presence server may use a subscriber/publisher model to providethe presence information for the users of the presence service. Wheneverthe presence information of a user changes, the presence server isnotified of the change by that user's computer system and in turnnotifies the subscribing users of the change. A subscribing user canthen decide whether to initiate an instant messaging conversation basedon the presence information of the intended participants. For example,if the presence information indicates that a publishing user iscurrently in a conference telephone call, then the subscribing user maydecide to send an instant message, rather than place a telephone call,to the publishing user. If the subscribing user, however, needs to calland speak with the publishing user, the subscribing user needs tomonitor the presence information of the publishing user to know when thecall can be placed. When the subscribing user notices that thepublishing user's presence information indicates that the telephoneconference has been concluded, the subscribing user can then place thetelephone call. RFC 2778 is a specification relating to presenceinformation in instant messaging systems. RFC 3856 is a specificationrelating to presence information using the Session Initiation Protocol(“SIP”).

It is not uncommon for a user to be signed into a collaboration serverusing many devices at the same time, thus creating multiple endpoints.For example, a user may simultaneously be signed into an instantmessaging server using a personal digital assistant, a wirelesstelephone, and a laptop computer. In this instance, each of theseendpoints contains pieces of information regarding the user, such aswhether the user is typing on a device, using the device to make a phonecall, etc., and the user's availability for communication or other formsof interaction with others at any instant in time. While currentpresence services may be suitable for providing a user's availability tocommunicate at a specific user endpoint, these presence services areunable to provide an accurate depiction of a user's availability tocommunicate when the user is signed into multiple endpoints.

SUMMARY

A method and system for aggregating user presence across multipleendpoints at a server is provided. A presence aggregation systemprovides a presence aggregation server that allows for the publicationof presence states of a publisher from the publisher's multipleendpoints. A presence state includes an availability value and anactivity. An activity may specify an activity taken and/or a customstring. For example, a user may publish a state that includes anavailability value that indicates that the user (e.g., publisher) isonline. When any one of the publisher's endpoints makes a presence statepublication on the presence aggregation server, the presence aggregationserver generates an aggregated state of the publisher (i.e., theavailability of the publisher aggregated across all of the publisher'sendpoints) and publishes the generated aggregated state to each of thepublisher's endpoints. The presence aggregation server may also providethe publisher's aggregated state to the subscribers of the publisher'saggregated state information.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram that illustrates components of a presenceaggregation system, according to some embodiments.

FIG. 2 is a data structure diagram that illustrates example logical datastructures of the presence aggregation system, according to someembodiments.

FIG. 3 is a flow diagram that illustrates the processing of the presenceaggregation system, according to some embodiments.

FIG. 4 is a flow diagram that illustrates the processing of theaggregation module in determining an aggregated machine state, accordingto some embodiments.

FIG. 5 is a flow diagram that illustrates the processing of theaggregation module in determining an aggregated availability, accordingto some embodiments.

FIG. 6 is a flow diagram that illustrates the processing of theaggregation module in determining a current activity, according to someembodiments.

DETAILED DESCRIPTION

A method and system for aggregating user presence across multipleendpoints at a server is provided. In some embodiments, a presenceaggregation system provides a presence aggregation server that allowsfor the publication of presence states of a publisher from any of thepublisher's multiple endpoints. A presence state includes anavailability value and an activity. An activity may specify an activitytoken and/or a custom string. For example, a user may publish a statethat includes an availability value that indicates that the user (e.g.,publisher) is online. As another example, a machine may specify that itis active by publishing a state that includes availability value thatindicates that the machine is online. When any one of the publisher'sendpoints publishes a presence state on the presence aggregation server,the presence aggregation server generates an aggregated presence state(also interchangeably referred to herein as an “aggregated state”) ofthe publisher (i.e., the availability of the publisher aggregated acrossall of the publisher's endpoints) and publishes the generated aggregatedstate to each of the publisher's endpoints. The presence aggregationserver may also provide the publisher's aggregated state to thesubscribers of the publisher's aggregated state information. In someembodiments, the presence aggregation server may generate an aggregatedstate of a publisher when a presence state publication for the publisherexpires. For example, a presence state publication may expire when anendpoint becomes offline. In some embodiments, the presence aggregationserver may generate an aggregated state of a publisher based onspecified triggers. For example, an endpoint may publish a presencestate that indicates that the publisher is going to be busy at 2:00 P.M.In this instance, the presence aggregation server may generate anaggregated state for the publisher at the indicated time.

The presence state publication focuses on the publisher. By focusing onthe publisher, the presence aggregation system provides a“person-centric” presence model in that the publisher is able to specifyhis or her presence for the desired modes of communication. Theperson-centric presence model simplifies the communication process byallowing a person to think in terms of “I want to talk to this person”instead of “I need to call the person's cell phone.” For example, thepublisher is able to indicate that communication by phone or anin-person meeting at the publisher's office is more convenient for thepublisher than sending an instant message. A subscriber receiving theaggregated state of a publisher is able to use this information to makedecisions on how to best communicate with the publisher. If theaggregated state of the publisher indicates that the publisher iscurrently away, the subscriber can send an instant message but will notbe upset if a reply is not received. In this manner, the presenceaggregation system allows a publisher to more accurately indicate theiravailability to communicate across all the publisher's endpoints, andthe subscribers of the publisher's aggregated state to obtain a betterindication of the availability and willingness of the publisher tocommunicate.

Throughout the description, the following terms will generally have thefollowing meanings:

The term “activity” refers to a descriptor for what a user is doing at amoment in time. For example, a calendaring application can publishcalendar type states that contain in-a-meeting event information.

The term “aggregated availability” refers to the availability associatedwith a user (e.g., publisher) across all of the user's endpoints.

The term “aggregated presence” refers to a combined presence of a useracross all of the user's endpoints. Aggregated presence can includeinformation beyond aggregated presence states. For example, aggregatedpresence can also include a machine's idle time, indication of location,etc.

The term “availability” refers to a user's willingness and ability tocommunicate. As such, a person's availability is a representation of how“available” the person is and/or whether the person can be interrupted.Availability is designated by a numerical value. The higher the number,the less reachable/available the person.

The term “callee” or “publisher” refers to a user that is the target ofthe presence-based communication (e.g., real-time communication). Thecallee or publisher is the person that publishes the presenceinformation.

The term “caller” or “subscriber” refers to the user that is viewing thepublished aggregated availability information. The caller or subscriberis the user that initiates the presence-based communication to thepublisher or callee.

The term “endpoint” refers to a single logon session of the user.Endpoints are typically synonymous with devices.

The term “presence” refers to information that is useful for determininga user's availability.

The term “state” refers to blocks of information that represent factorsthat influence a person's willingness and availability to communicate.

In some embodiments, the presence aggregation server provides containersfor publishing presence information. The presence aggregation serverprovides each publisher a “status” container, and only the publisher haspermissions to view the contents of his or her status container. Eachstatus container contains a collection of zero, one or more presencestate publications for its respective publisher. The presenceaggregation server monitors the status containers for a change in thestate of a publisher (e.g., a presence state publication that changesthe publisher's state). Upon detecting a change in the publisher'sstate, the presence aggregation server generates an aggregated state(i.e., an aggregated availability and/or a current activity) of thepublisher and publishes an indication of the aggregated state in thepublisher's status container, thus notifying each of the publisher'sendpoints of the published aggregated state. The presence aggregationserver may also determine the publisher's computing device (alsoreferred to herein as a “machine”) that is the most active, and publishthis information to the publisher's status container, thus notifyingeach of the publisher's endpoints of the publisher's most activemachine. Each of the publisher's endpoints can then use this informationto, by way of example, determine whether or not to “auto-accept” arequest to communicate. The publisher's computing device is a deviceused by the publisher to create an endpoint.

The presence aggregation server allows each publisher to define acollection of one or more containers, to specify an access control list(ACL) for each container, and to specify the publications that are to beincluded in each container. The ACL specifies the entities, alsoreferred to as “members,” who are allowed to subscribe to receive thepublications made to each container. For example, the publisher mayspecify members of a container by specifying membership types ofindividual entities (e.g., Joe Smith), a group of entities (e.g.,Project A Marketing Team), entities with a common characteristic (e.g.,within domain acme.com), and so on. The presence aggregation serverallows entities to subscribe to receive a publisher's publications,including the subscriber's aggregated state and other published presenceinformation. If the subscribing entity is a member of a container asdetermined by the container's ACL, then the presence aggregation serveradds that entity as a subscriber of that container. The presenceaggregation server then notifies the subscribers of the container of thepublications made to that container. The publication may be thepublisher's aggregated state as well as other presence information. Forexample, when the presence aggregation server generates an aggregatedstate of the publisher, the presence aggregation server can publish anindication of the aggregated state in each of the publisher'scontainers, thus notifying the subscribers of the publisher's aggregatedstate. The presence aggregation server may allow a publisher to publishpresence information directly to the publisher's containers. Forexample, a publisher may define a container that is to be made availableto subscribers who are coworkers and may define another container thatis to be made available to all other subscribers. In this example, thepublisher may want to publish more detailed presence information in thecontainer that is available to coworkers. For example, in addition tothe aggregated state, a publisher may also want to inform the coworkersthat the publisher is “in a meeting with John,” while not providing thisadditional piece of information to the others.

In some embodiments, a presence state publication may be of a type“user,” “machine,” “phone,” “calendar,” “conference,” or “generic,” asshown in Table 1 below.

TABLE 1 State Type Description User A preset state a publisher canmanually set Machine A state of the endpoint machine (endpoint device)Phone The state of a publisher's phone Calendar Events in a publisher'sschedule (e.g., Outlook schedule) Conference Triggered when a publisheris in a multiparty conversation or if the publisher is presenting in acollaborative session Generic All other states

A user state is manually provided or specified by a publisher and, assuch, provides an indication of the publisher's intent. For example, thepresence aggregation system's client application executing on thepublisher's machine, and which the publisher may have used to create anendpoint, may provide a user interface through which the publisher canaccess a list of user states, such as those listed in Table 2 below.

TABLE 2 User State Availability Value Description Online 3500 Publisheris reachable Busy 6500 Publisher is busy Do Not Disturb 9500 Publishershould not be interrupted Be Right Back 12500 Publisher is not currentlyreachable Away 15500 Publisher is not at their desk Appear Offline 18500Publisher wants to be offline

As shown by the example user states in Table 2, a publisher may indicatehis or her intent to communicate as “Online,” “Busy,” “Do Not Disturb,”“Be Right Back,” “Away,” and “Appear Offline.” Each user state has acorresponding availability value that is a number that represents theavailability of the subscriber as indicated by the user state from moreavailable to less available, where the larger availability valuecorresponds to the less available state. For example, from amongst thesix user states listed in Table 2, “Online” is the most available userstate and “Appear Offline” is the least available user state. Thepublisher can specify a user state by selecting one of the user statesfrom the displayed list. When a publisher selects one of the user statesfrom the displayed list, the client application determines theavailability value that corresponds to the specified user state, andpublishes the availability value as the publisher's user state in thepublisher's status container on the presence aggregation server. Forexample, if the publisher manually specifies a user state of “Online,”the specified user state will be published in the publisher's statuscontainer as a user state availability value of 3500 (e.g., user state;avail=3500). When a user state is published, the presence aggregationserver stamps the publication with a publication time.

A machine state provides an indication of whether the publisher isreachable on the machine. In some embodiments, each endpoint publishes amachine state. For example, the client application may monitor thepublisher's machine for events such as keyboard activity or inactivity,mouse or pointing device activity or inactivity, activation of screensaver or machine lock, and other events that provide an indication ofthe use of the machine. When such an event is detected, the clientapplication determines the availability value that corresponds to themachine state, and publishes the availability value as the publisher'smachine state in the publisher's status container on the presenceaggregation server. A list of example machine states and correspondingavailability values and optional activity tokens is provided in Table 3below.

TABLE 3 Machine Availability State Value Activity Token DescriptionActive 3500 NULL Publisher is actively using the device and is reachableInactive 3750 Inactive Publisher has not used the device but is stilllikely to be reachable Unknown 3750 Inactive The device cannot determineif the publisher is reachable Away 15500 NULL Publisher is probably notat the device and is not reachable Off 18500 NULL Publisher is notlogged on and definitely not reachable

As shown in Table 3, an endpoint may indicate the machine state as“Active,” “Inactive,” “Unknown,” “Away,” and “Off.” Similar to the userstates listed in Table 2, the machine states listed in Table 3 areranked according to their indication of availability from more availableto less available, where the larger availability value corresponds tothe less available state. Moreover, from Tables 2 and 3, it can be seenthat the machine state of “Away” indicates a less available state that auser state of “Do Not Disturb.” The activity token, when present, is atext string that represents the particular machine state. The activitytoken is typically provided by the publisher (e.g., the clientapplication that published the machine state). For example, the clientapplication can determine that it is being currently used and, fromthis, determine a machine state of “Active.” In this example, the clientapplication can publish a machine state in the publisher's statuscontainer on the presence aggregation server as a machine stateavailability value of 3500 (e.g., machine state; avail=3500; activitytoken=NULL). In another example, the client application can monitorhardware activity to determine a machine state. When a machine state ispublished, the presence aggregation server stamps the publication with apublication time.

A phone state indicates the state of a publisher's phone. For example,the client application may detect that the publisher is currentlyengaged in a voice over Internet (VoIP) call and publish a phone state.A list of example phone state availability values and correspondingoptional activity tokens and custom strings is provided in Table 4below.

TABLE 4 Availability Value Activity Token Custom String Description 6500In a call In a 1 on 1 User is speaking with conversation one person 6750In a conference In a multiparty User is speaking with conversation morethan one person

Similar to the user states listed in Table 2 and the machine stateslisted in Table 3, the phone states listed in Table 4 are rankedaccording to their indication of availability from more available toless available, where the larger availability value corresponds to theless available state. The activity token, when present, is a text stringthat represents the particular phone state. The custom string, whenpresent, is a text string that further describes the particular phonestate. For example, the custom string may describe the phone state in aspecific language, such as Japanese. The activity token and the customstring are typically provided by the publisher (e.g., the clientapplication that published the phone state). For example, the clientapplication can determine that the publisher is currently conducting aone-on-one conversation. In this example, the client application canpublish a phone state in the publisher's status container on thepresence aggregation server as a phone state availability value of 6500(e.g., phone state; avail=6500; activity token=“In a call”; customstring=“In a 1 on 1 conversation”). When a phone state is published, thepresence aggregation server stamps the publication with a publicationtime.

A calendar state indicates the state of a publisher's calendar. Forexample, the client application can interact with a calendaringapplication to determine that the publisher is free, in a meeting, outof the office, etc., and publish this information as a calendar state. Alist of example calendar state availability values and correspondingoptional activity tokens and custom strings is provided in Table 5below.

TABLE 5 Availability Value Activity Token Custom String Description 3500NULL Free Publisher has no meeting 3500 NULL Tentative Publisher has ameeting they have not accepted 6500 In a meeting In a meeting Publisherhas accepted a meeting 3500 Out of Office Out of the Publisher is not inthe Office office

Similar to the user states listed in Table 2, the machine states listedin Table 3, and the phone states listed in Table 4, the calendar statesin Table 5 are ranked according to their indication of availability frommore available to less available, where the larger availability valuecorresponds to the less available state. The activity token, whenpresent, is a text string that represents the particular calendar state.The custom string, when present, is a text string that further describesthe particular calendar state. For example, the custom string mayprovide additional details regarding the particular calendar state thatis not provided by the activity token. The activity token and the customstring are typically provided by the publisher (e.g., the clientapplication that published the calendar state). For example, the clientapplication can determine that the publisher has no meetings. In thisexample, the client application can publish a calendar state in thepublisher's status container on the presence aggregation server as acalendar state availability value of 3500 (e.g., calendar state;avail=3500; activity token=“NULL”; custom string=“Free”). When acalendar state is published, the presence aggregation server stamps thepublication with a publication time.

A conference state indicates the state of a publisher's conferencingactivities. For example, the client application may detect that thepublisher is currently participating in a conference and publish aconference state. A list of example conference state availability valuesand corresponding optional activity tokens and custom strings isprovided in Table 6 below.

TABLE 6 Availability Value Activity Token Custom String Description 9500NULL Presenting Participant in full screen mode 6900 Urgent- UrgentPublisher is presenting Interruptions- interruptions (Do-Not-Disturb)but Only only certain subscribers should see a “Busy” availability 6750In a multiparty In a conference Publisher is speaking conference withmore than one person in the same conversation in a mode other thanInstant Messaging

Similar to the user states listed in Table 2, the machine states listedin Table 3, the phone states listed in Table 4, and the calendar stateslisted in Table 5, the conference states listed in Table 6 are rankedaccording to their indication of availability from more available toless available, where the larger availability value corresponds to theless available state. The activity token, when present, is a text stringthat represents the particular conference state. The custom string, whenpresent, is a text string that further describes the particularconference state. For example, the custom string may describe theconference state in a specific language, such as Japanese, or provideadditional details regarding the particular conference state that is notprovided by the activity token. The activity token and the custom stringare typically provided by the publisher (e.g., the client applicationthat published the conference state). By way of example, the clientapplication may detect that a conferencing application, such asMICROSOFT's POWERPOINT, executing on the publisher's machine is in “fullscreen” mode. From this, the client application may determine that thepublisher is currently presenting in a conference. In this example, theclient application can publish a conference state in the publisher'sstatus container on the presence aggregation server as a conferencestate availability value of 9500 (e.g., conference state; avail=9500;activity token=“NULL”; custom string=“Presenting”). When a conferencestate is published, the presence aggregation server stamps thepublication with a publication time.

Generic states include the events that are not published as either auser state, a device state, a phone state, a calendar state, or aconference state. For example, the client application executing on theuser's machine may detect an event that is not a user state, a devicestate, a phone state, a calendar state, or a conference state. In thisinstance, the client application can publish the event as a genericstate in the publisher's status container on the presence aggregationserver. In addition to indicating that the publication is a genericstate publication and providing an availability value, the clientapplication may also provide an activity token and/or a custom stringthat represents and/or additionally describes the published genericstate. When a generic state is published, the presence aggregationserver stamps the publication with a publication time.

In some embodiments, the client application may provide an applicationprogram interface (API) which allows events detected by otherapplications to be published. For example, applications such as acalendaring application, a phone application (e.g., VoIP application),another conferencing application, etc., can detect events and requestthat the client application publish the detected events in thepublisher's status container on the presence aggregation server.

In some embodiments, a third-party application or device may directlypublish events in the publisher's status container on the presenceaggregation server. For example, a private branch exchange (PBX) devicemay be knowledgeable of the presence aggregation server and may have thenecessary privileges (e.g., credentials) to publish presence informationfor a publisher in the publisher's status container on the presenceaggregation server. When the PBX device detects an event, such as thepublisher being currently engaged in a telephone call, the PBX devicecan publish the detected event by determining an appropriateavailability value that represents the event. The PBX device can thenpublish the availability value as a generic state in the publisher'sstatus container on the presence aggregation server. The PBX device mayalso provide an activity token and/or a custom string that representsand/or additionally describes the published generic state.

In some embodiments, the presence aggregation server determines anaggregated availability of a publisher by considering the publisher'spresence state publications across all of the publisher's endpoints, andpublishes the determined aggregated availability. The presenceaggregation server monitors the status containers for changes to thepublishers' state. Upon detecting a change to a publisher's state (e.g.,a presence state publication to the publisher's status container), thepresence aggregation server generates an aggregated availability for thepublisher as the least available state across all of the publisher'sendpoints. The presence aggregation server identifies the most availablemachine state from the published machine states, and only uses the mostavailable machine state to perform the aggregation. To determine thepublisher's aggregated availability, the presence aggregation serverchecks the publisher's status container for a publication of a userstate. In the case where there is a user state publication, the presenceaggregation server extracts the publication time of the user statepublication, and sorts the other presence state publications (theidentified most available machine state publication, phone statepublications, calendar state publications, conference statepublications, and generic state publications) in the status container bypublication time, and eliminates the presence state publications thatare older than the user state publication. From the remaining presencestate publications, the presence aggregation server extracts theavailability value from the least available state, and assigns thisavailability value as the publisher's aggregated availability. In thecase where a user state publication is not present in the statuscontainer, the presence aggregation server extracts the availabilityvalue from the least available state from amongst the most availablemachine state publication, phone state publications, calendar statepublications, conference state publications, and generic statepublications, and assigns this availability value as the publisher'saggregated availability. The presence aggregation server then publishesthe generated aggregated availability (e.g., a value representing theaggregated availability, an indication of an icon representing theaggregated availability, a default string representing the aggregatedavailability, etc.) in the publisher's status container, which causeseach of the publisher's endpoints to be notified of the publisher'saggregated availability. The aggregated availability can then bedisplayed at each endpoint. The presence aggregation server may alsopublish the generated aggregated availability in one or more of thepublisher's other containers. This causes the publisher's aggregatedavailability to be sent to the subscribers who have subscribed to thecontainers, thus notifying the subscribers of the publisher's aggregatedavailability.

Table 7 below contains a mapping of availability values to correspondingaggregated availabilities, default strings, and descriptions.

TABLE 7 Aggregated Availability Availability Default String Value RangeDescription Online Online 3000-3999 Publisher is reachable Busy Busy6000-6999 Publisher is reachable but is engaged in another task Do NotDo Not Disturb 9000-9999 Publisher is reachable but Disturb does notwant to be interrupted Temporarily Temporarily 12000-12999 Publisher istemporarily Away Away probably not reachable Away Away 15000-15999Publisher is probably not reachable Offline Offline 18000-18999Publisher is not reachable

As shown in Table 7, a range of availability values maps to eachaggregated availability. For example, the availability values in therange 3000-3999 map to the aggregated availability “Online.” Mapping arange of availability values to a single aggregated availability allowsfor a ranking of availability values within a class of availabilities.For example, the phone state “In a multiparty conversation” in Table 4above and the calendar state “In a meeting” above in Table 5 above willboth map to the same aggregated availability “Busy.” Even though both ofthese states result in the same aggregated availability, the phone state“In a multiparty conversation” is ranked lower (i.e., less available)than the calendar state “In a meeting” because of its largeravailability number (6750>6500). As such, if the publisher's aggregatedavailability is to be chosen from these two states, the phone state “Ina multiparty conversation” will be selected as the publisher'saggregated availability.

In some embodiments, the presence aggregation server determines acurrent activity that a publisher is engaged in and publishes thisinformation. The presence aggregation server may publish a currentactivity as part of the aggregated state. To determine the currentactivity for a publisher, the presence aggregation server identifies themost available machine state from the published machine states. Thepresence aggregation server then checks the publisher's status containerfor a publication of a user state. In the case where there is a userstate publication, the presence aggregation server extracts thepublication time of the user state publication, and sorts the otherpresence state publications (the identified most available machine statepublication, phone state publications, calendar state publications,conference state publications, and generic state publications) in thestatus container by publication time, and eliminates the statepublications that are older than the user state publication. From theremaining presence state publications, the presence aggregation serverremoves the presence state publications that do not have a correspondingactivity token or custom string (i.e., the state publications that donot include an activity). If there are no remaining presence statepublications, the presence aggregation server publishes an indicationthat there is no current activity. If there are remaining presence statepublications, the presence aggregation server selects the activity fromthe least available of the remaining presence state publications as thecurrent activity. The presence aggregation server then publishes thecurrent activity of the publisher in the publisher's status container.The presence aggregation server may also publish the current activity inone or more of the publisher's other containers. In this instance wherethe presence aggregation server publishes an indication that there is nocurrent activity, the endpoint (e.g., an application executing on theendpoint) may select the default string that represents the publisher'saggregated availability as the publisher's current activity.

In some embodiments, a presence state publication may include multipleactivities. Each activity included in the publication may have acorresponding indicator that specifies a condition under which theparticular activity is to be considered valid. For example, apublication may indicate that the publisher's activity is to be “Out ofthe Office” if the availability value is greater than 15000, and thatthe activity is to be “Online” otherwise. As another example, apublication may indicate that the publisher's activity is to be “Out ofthe Office” between 10 a.m. and 2 p.m., and that the activity is to be“Free” at the other times during the day. One skilled in the art willappreciate that the condition indication for an activity may bespecified in other ways. For example, a condition indicator may includea combination of availability value ranges and a range of times.

In some embodiments, the presence aggregation server determines anaggregated machine state for a publisher and publishes this information.The presence aggregation server identifies the publisher's most activemachine state as the publisher's aggregated machine state, and publishesthis information in the publisher's status container. The presenceaggregation server may also identify as the most active machine themachine from which the most active machine state was published, andpublish an indication of the most active machine in the publisher'sstatus container. Each of the publisher's endpoints can use thisinformation in multiple points of presence scenarios, for example, toautomatically respond to a request that have been received by all of thepublisher's endpoints.

FIG. 1 is a block diagram that illustrates components of a presenceaggregation system, according to some embodiments. A presenceaggregation system 102 is coupled to entity devices 104 via a network106. The entity devices correspond to entities that may be publishers orsubscribers. The presence aggregation system includes a receive updatemodule 108, an update publication module 110, an add publication module112, a receive subscription request module 114, an add subscriptionmodule 116, a create container module 118, a container store 120, anaggregation module 122, and an expire publications module 124. Some orall of the modules may be provided on a presence aggregation server ormultiple presence aggregation servers. The container store contains thecontainers of the publishers (created by the create container module)and other data structures used by the presence aggregation system. Thereceive update module is invoked when a request to update a publicationis received from a publisher. The receive update module invokes theupdate publication module to update the publication and the addpublication module to add a new publication to a container. The receivesubscription request module is invoked when a request is received froman entity to subscribe to a container of a publisher. The receivesubscription request module invokes the add subscription module tosubscribe the entity to the specified container or containers. Theaggregation module processes the presence state publications in apublisher's status container to generate an aggregated state of thepublisher. The expire publications module is periodically invoked by thepresence aggregation system to clean up the expired (stale) publicationsin the containers in the container store. Although not shown in FIG. 1,the entity devices include components of the presence aggregation systemto define containers and their ACLs, to send publication updates, tosend subscription requests, to receive notifications of updates topublications, and to receive publications from the presence aggregationsystem.

The network is typically a communications link that facilitates thetransfer of electronic content between the attached devices. In someembodiments, the network includes the Internet. It will be appreciatedthat the network may be comprised of one or more other types ofnetworks, such as a local area network, a wide area network, apoint-to-point dial-up connection, a wireless network, and the like.

The computing devices on which the presence aggregation system may beimplemented may include a central processing unit, memory, input devices(e.g., keyboard and pointing devices), output devices (e.g., displaydevices), and storage devices (e.g., disk drives). The memory andstorage devices are computer-readable media that may containinstructions that implement the presence aggregation system. Inaddition, the data structures and message structures may be stored ortransmitted via a data transmission medium, such as a signal on acommunications link. Various communications links may be used, such asthe Internet, a local area network, a wide area network, apoint-to-point dial-up connection, a cell phone network, and so on.

Embodiments of the presence aggregation system may be implemented invarious operating environments that include personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, programmable consumer electronics, digitalcameras, network PCs, minicomputers, mainframe computers, distributedcomputing environments that include any of the above systems or devices,and so on. The user devices may be cell phones, personal digitalassistants, smart phones, personal computers, programmable consumerelectronics, digital cameras, and so on.

The presence aggregation system may be described in the general contextof computer-executable instructions, such as program modules andcomponents, executed by one or more computers or other devices.Generally, program modules include routines, programs, objects,components, data structures, and so on that perform particular tasks orimplement particular abstract data types. Typically, the functionalityof the program modules may be combined or distributed as desired invarious embodiments.

FIG. 2 is a data structure diagram that illustrates example logical datastructures of the presence aggregation system, according to someembodiments. The data structure includes a publisher table 202 thatincludes an entry for each publisher. Each entry identifies a publisherand points to the publisher's container table 204. The publisher'scontainer table contains an entry for each container of thecorresponding publisher. Each entry identifies the container (e.g., byname) and contains an ACL, a subscriber list, and a publication list.The ACL specifies the entities who are allowed to subscribe to thecorresponding container. The subscriber list identifies the subscriberswho are subscribed to the corresponding container. The publication listcontains an entry for each publication of the container. When apublication is made in a container, the presence aggregation system usesthe subscriber list to identify the subscribers that are to be notified.When an entity subscribes to a container, the presence aggregationsystem uses the ACL to determine whether to grant or deny thesubscription. One skilled in the art will appreciate that this is onlyone example of the logical layout of data structures of the presenceaggregation system. The data structures of the presence aggregationsystem may be tailored to the space/computation requirements of thepresence aggregation system. For example, the subscriber list may beprovided in a separate table, such as a subscriber table. Each entry inthe subscriber table may specify a publisher, a subscriber, and a listof publications (including their versions). The presence can use thecombination of tables to determine what versions of the publicationsshould be seen by the subscribers.

FIG. 3 is a flow diagram that illustrates the processing of the presenceaggregation system, according to some embodiments. The presenceaggregation system monitors the status containers for changes to thestates of publishers. When a change in a state of a publisher isdetected, the system, in block 302, determines an aggregated machinestate of the publisher and publishes the aggregated machine state in thepublisher's status container. In block 304, the system determines anaggregated availability of the publisher. In block 306, the systemdetermines the current activity of the publisher. In block 308, thesystem publishes the aggregated availability and the current activity asthe aggregated state of the publisher in the publisher's statuscontainer and the publisher's other containers which have beendesignated as being appropriate for the publication of the aggregatedstate. The publisher can designate the containers that are appropriatefor the publication of the aggregated state.

One skilled in the art will appreciate that, for this and otherprocesses and methods disclosed herein, the functions performed in theprocesses and methods may be implemented in differing order.Furthermore, the outlined steps are only exemplary, and some of thesteps may be optional, combined with fewer steps, or expanded intoadditional steps without detracting from the essence of the invention.

FIG. 4 is a flow diagram that illustrates the processing of theaggregation module in determining an aggregated machine state, accordingto some embodiments. The aggregation module processes the machine statepublications in a publisher's status container and notifies thepublisher's endpoints of the single aggregated machine state for thepublisher's most active machine. In block 402, the aggregation moduleselects the most active machine state (i.e., the machine statepublication having the lowest availability value). In block 404, theaggregation module checks to determine whether there are multiple mostactive machine states. If there is more than one most active machinestate, then, in block 404, the aggregation module selects as the mostrecently published most active state. In block 408, the aggregationmodule returns the most active machine state. In some embodiments, theaggregation module identifies the machine that published the most activemachine state, and returns an indication of this machine (i.e., the mostactive machine). If two machines (e.g., respective endpoints on the twomachines) published the same machine state that was determined to be themost active machine state, the aggregation module identifies as the mostactive machine the machine that most recently published the most activemachine state. For example, if a Machine A published an Active machinestate at 1:00 PM and a Machine B published an Active machine state at1:30 PM, the aggregation module identifies Machine B as the most active.

FIG. 5 is a flow diagram that illustrates the processing of theaggregation module in determining an aggregated availability, accordingto some embodiments. In block 502, the aggregation module determines avalid set of states from which to generate an aggregated availability.The valid set of states may include the most active machine state andany user state, phone states, calendar states, conference states, andgeneric state publications in the subscriber's status container. Inblock 504, the aggregation module checks to determine if a user state ispublished. If the aggregation module determines that a user statepublication is present in the status container, then, in block 506, theaggregation module removes the states that are older than the user statefrom the valid set of states. For example, the aggregation moduleidentifies the states in the valid set of states that have publicationtimes that are older than the publication time of the user state, andremoves these older states from the valid set of states. If, in block504, the aggregation module determines that a user state is notpublished, or subsequent to removing from the valid set of states thestates that are older than the published user state in block 506, theaggregation module, in block 508, selects as the aggregated availabilitythe least available state (e.g., the state having the highestavailability value) from the valid set of states. In block 510, theaggregation module returns the aggregated availability.

FIG. 6 is a flow diagram that illustrates the processing of theaggregation module in determining a current activity, according to someembodiments. In block 602, the aggregation module determines a valid setof states from which to determine the current activity of a publisher.The valid set of states may include the most active machine state andany user state, phone states, calendar states, conference states, andgeneric state publications in the subscriber's status container. Inblock 604, the aggregation module removes from the valid set of statesthe states that do not have a corresponding activity token. For example,some publications may not specify an activity token. In block 606, theaggregation module checks to determine whether the valid set of statesis empty. If the valid set of states is not empty, then, in block 608,the aggregation module selects the activity from the least availablestate as the current activity. In block 610, the aggregation modulereturns the current activity. Otherwise, if the aggregation moduledetermines that the valid set of states is empty (block 606), then, inblock 612, the aggregation module returns an indication of no currentactivity.

From the foregoing, it will be appreciated that specific embodiments ofthe presence aggregation system have been described herein for purposesof illustration, but that various modifications may be made withoutdeviating from the spirit and scope of the invention. For example, oneskilled in the art will appreciate that a publisher may publish presenceinformation directly to one or more of the publisher's containers. Inresponse to such a publication, the presence aggregation system cannotify the subscribers who have subscribed to these containers thepresence information published by the publisher. As another example, oneskilled in the art will appreciate that a publication may have acorresponding expire type that indicates the condition or conditionsunder which to expire the publication. For example, the expire type mayindicate that a publication is to be expired after a duration of time,after the publisher logs off from all of the publisher's endpoints, whenthe publisher is no longer using any of the publisher's machines, etc.Accordingly, although the subject matter has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

We claim:
 1. A method performed by a computing device for aggregatingpresence information of a publisher, the method comprising: identifyinga user state publication of the publisher that was most recentlypublished, the user state publication representing availability of thepublisher as specified by the publisher and having an availabilityvalue; identifying other state publications of the publisher publishedafter the identified user state publication, the other statepublications representing availability of the publisher as derived frommonitoring the publisher and having an availability value; identifyingfrom the availability values of the identified user state publicationand the identified other state publications a least available state; andgenerating an aggregated state of the publisher indicating overallavailability of the publisher based on the identified least availablestate so that the aggregated state is derived from the identified userstate publication and the identified other state publications.
 2. Themethod of claim 1 wherein at least one of the other state publicationsis a machine state publication.
 3. The method of claim 1 wherein atleast one of the other state publications is published by a third partyon the publisher's behalf.
 4. The method of claim 1 wherein at least oneof the other state publications is published by an endpoint of thepublisher.
 5. The method of claim 1 further comprising publishing theaggregated state to subscribers to the presence information of thepublisher.
 6. The method of claim 5 wherein endpoints of the publisherare subscribers to the presence information of the publisher.
 7. Themethod of claim 5 wherein a state publication indicates an activity andfurther comprising upon detecting a change in the publisher's state;publishing a current activity of the publisher.
 8. The method of claim 1wherein the computing device is an endpoint of the publisher.
 9. Acomputing device for aggregating presence information of a publisher,the computing device comprising: a computer-readable medium storingcomputer-executable instructions adapted to control a processor toaccess a collection of presence state publications for the publisher,each presence state publication having an availability value and anactivity, the presence state publications including user statepublications and other state publications, the user state publicationsrepresenting availability of the publisher as manually specified by thepublisher and the other state publications representing availability ofthe publisher as derived from monitoring the publisher, each presencestate publication having a publication time; identify from thecollection a user state publication with the latest publication time;identify from the collection other state publications with a publicationtime that is later the publication time of the identified user statepublication; and generate an aggregated state of the publisherindicating overall availability of the publisher based on a leastavailable state derived from the identified user state publication andthe identified other state publications; and a processor for executingthe computer-executable instructions stored in the computer-readablemedium.
 10. The computing device of claim 9 wherein at least one of theother state publications is published by a computer of a third party onthe publisher's behalf.
 11. The computing device of claim 9 wherein atleast one of the other state publications is published by an endpoint ofthe publisher.
 12. The computing device of claim 9 wherein thecomputer-executable instructions are further adapted to control aprocessor to publish the aggregated state to subscribers to the presenceinformation of the publisher.
 13. The computing device of claim 12wherein endpoints of the publisher are subscribers to the presenceinformation of the publisher.
 14. The computing device of claim 12wherein a state publication indicates an activity and wherein thecomputer-executable instructions further adapted to control a processorto upon detecting a change in the publisher's state, publish a currentactivity of the publisher.
 15. The computing device of claim 12 whereinthe computing device is an endpoint of the publisher.
 16. The computingdevice of claim 12 wherein the computing device is a presence server.17. A presence system for aggregating presence information of apublisher, the presence system comprising: a computer-readable mediumstoring a collection of presence state publications for the publisher,each presence state publication having a state indicated by anavailability value and an activity, the presence state publicationsincluding a user state publication and other state publications, theuser state publication representing availability of the publisher asspecified by the publisher and the other state publications representingavailability of the publisher as derived from monitoring the publisher;a computer-readable medium storing computer-executable instructionsadapted to control a processor to identify from the collection a userstate publication of the publisher that was most recently published;identify other state publications of the publisher published after theidentified user state publication; identify from the availability valuesof the identified user state publication and the identified other statepublications a least available state; generate an aggregated state ofthe publisher indicating overall availability of the publisher based onthe identified least available state so that the aggregated state isderived from the identified user state publication and the identifiedother state publications; and publish the aggregated state tosubscribers to presence information of the publisher; and a processorfor executing the computer-executable instructions stored in thecomputer-readable medium.
 18. The presence system of claim 17 whereinendpoints of the publisher are subscribers to the presence informationof the publisher.
 19. The presence system of claim 17 wherein thesubscribers include endpoints of the publisher.
 20. The presence systemof claim 17 wherein a state publication indicates an activity andwherein the computer-executable instructions are further adapted tocontrol a processor to upon detecting a change in the publisher's state,publish a current activity of the publisher.